Systems and Methods for Automatically Testing the Communication Between Wireless Power Transmitter and Wireless Power Receiver

ABSTRACT

Systems and methods to use software to automatically test the communication between wireless power transmitter and wireless power receiver are described. The described systems include one or more wireless power transmitters, one or more wireless power receivers and one or more electronic devices. Electronic devices may be able to communicate with wireless power transmitters and wireless power receivers using suitable communications channels. The disclosed methods may be employed for antenna direction management and for transmission of power from transmitter to receiver in a wireless power transmission system.

BACKGROUND

1. Field of the Disclosure

The present disclosure relates in general to wireless power transmission systems, and more specifically to methods for testing the communication between power transmitters and power receivers.

2. Background Information

The communication between a wireless power transmitter and a wireless power receiver of a wireless power transmission system may encounter unexpected or unpredictable errors due to conditions external to the system, due to defects within software design of the system, or due to degradation or unexpected operation of system hardware. The wireless power transmission system software may have communication error detection and correction methods so that normal operation of said system may continue in the event of any error.

This communication between the transmitter and the receiver is essential for wireless transmission of power from power transmitter to power receiver because transmitter uses communication connection with receiver to determine if the receiver is nearby or within power transmission range, to read the amount of power that the receiver is presently receiving and monitor this value while adjusting the direction of the transmitter's array of power transmission antennas to maximize power received by the receiver, and to command the receiver to electrically connect to its client device to transmit power to it, or disconnect when not powering it.

One limitation of wireless power transmission systems may be that defects in the system software may not be corrected and may cause interruption or unwanted cessation of normal operation of said system, if the system software is not tested for error conditions, if testing cannot be done manually, or if manual testing is inadvertently not done.

Another drawback may be that the failure of the system software to correctly respond to these error conditions may cause interruption or unwanted cessation of normal operation of the system if any error condition only occurs infrequently, and may only be detected by automatic test software.

The above mentioned problems, if not detected by automatic testing, may occur during system design development, during demonstrations, during production burn-in, or in the field of use after product installation during product normal operation.

Thus, there is a need for automatic test software that tests cases which cannot be tested manually or tests cases which occur so infrequently that it is not practical or there is not enough time to test manually.

SUMMARY

Systems and methods to use software to automatically test the communication between a wireless power transmitter and a wireless power receiver are disclosed. The disclosed systems and methods may be employed for antenna direction management and for wireless transmission of power from transmitter to receiver in a wireless power transmission system.

The disclosed systems may include power transmitters, power receivers, electronic devices, and suitable remote system managers.

According to one embodiment, the disclosed methods may be employed to perform an automatic self-test built in to power transmitters and power receivers. The self-test may be automatically run when a wireless power transmission system boots, or in response to a command from the system user.

The self-test may automatically establish communication connections between a power transmitter and each power receiver, and then may automatically continually begin testing the communication of all types of messages. Periodically, unexpected disconnection followed by re-connection and re-establishment of communication between power transmitter and power receiver may also be tested. Communication may be in real-time.

Counts of all actions and operations, performed by the wireless power transmission system while testing connections and communication, may be stored in metrics counters within a system database. When the test is complete, the metrics counters may be compared with expected values. If the metrics counters match the expected values, then test passes, otherwise test fails. Wireless power transmission system may report to the user the outcome of the test. Other methods may be employed to compare actions or operations with what is expected.

A user command may be employed to initiate a long term test of communication between a power transmitter and a power receiver to detect defects that may only occur infrequently. For example, the test may be performed overnight, over the weekend, or longer, among others.

Numerous other aspects, features and benefits of the present disclosure may be made apparent from the following detailed description taken together with the drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure can be better understood by referring to the following figures. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the disclosure. In the figures, reference numerals designate corresponding parts throughout the different views.

FIG. 1 illustrates a wireless power transmission example situation using pocket-forming, according to an exemplary embodiment.

FIG. 2 illustrates a component level embodiment for a transmitter, according to an exemplary embodiment.

FIG. 3 illustrates a component level embodiment for a receiver, according to an exemplary embodiment.

FIG. 4 illustrates an exemplary embodiment of a wireless power network including a transmitter and wireless receivers, according to an exemplary embodiment.

FIG. 5 shows a wireless power transmission network diagram, according to an exemplary embodiment.

FIG. 6 is a flowchart showing a method for automatic initiation of a self-test of a power transmitter software at boot, according to an exemplary embodiment.

FIG. 7 is a flowchart showing a method for automatic initiation of a self-test during a normal operation of a power transmitter, according to an exemplary embodiment.

FIG. 8 is a flowchart showing a method for manually initiated power transmitter self-test, according to an exemplary embodiment.

FIG. 9 is a flowchart showing a method for performing a self-test of a power transmitter, according to an exemplary embodiment.

DETAILED DESCRIPTION

The present disclosure is here described in detail with reference to embodiments illustrated in the drawings, which form a part here. Other embodiments may be used and/or other changes may be made without departing from the spirit or scope of the present disclosure. The illustrative embodiments described in the detailed description are not meant to be limiting of the subject matter presented here.

DEFINITIONS

As used here, the following terms may have the following definitions:

“Adaptive pocket-forming” refers to dynamically adjusting pocket-forming to regulate power on one or more targeted receivers.

“App” refers to a software application that is run on a mobile, laptop, desktop, or server computer.

“BTLE”, or “BLE”, refers to Bluetooth low energy communication hardware and/or software.

“Charge”, or “Charging”, refers to the conversion of RF energy into electrical energy by a receiver, using an antenna, where the electrical energy may be transmitted through an electrical circuit connection from the receiver to an electrically connected client device, where the transmitted energy may be used by the device to charge its battery, to power its functions, or any suitable combination.

“LAN” refers to wired or wireless Local Area Network.

“Null-space” refers to areas or regions of space where pockets of energy do not form because of destructive interference patterns of RF waves.

“Operator” refers to a person who installs or operates the wireless power transmission system.

Operator may also be a system user.

“Pairing” refers to the association, within the wireless power transmission system's distributed system database, of a single electronic client device with a single power receiver. In one or more embodiments, this may allow a system to determine from said association which power receiver to transmit power to in order to charge said client device upon receiving a command, from a user or automatic system process, that a client device is to be charged.

“Pocket-forming” refers to generating two or more RF waves which converge in 3-D space, forming controlled constructive and destructive interference patterns.

“Pockets of energy” refers to areas or regions of space where energy or power may accumulate in the form of constructive interference patterns of RF waves.

“Power” refers to electrical energy, where “wireless power transmission” may be synonymous of “wireless energy transmission”, and “wireless power transmission” may be synonymous of “wireless energy transmission”.

“Receive identification” refers to an identification number or alphanumeric code or credential that is unique to a specific receiver.

“Receiver” refers to a device including at least one antenna element, at least one rectifying circuit and at least one power converter, which may utilize pockets of energy for powering, or charging an electronic device.

“System” refers to a wireless power transmission system that wirelessly transmits power from a transmitter to a receiver.

“System Computer” refers to one of the computers of a wireless power transmission system; is part of the communication network between all computers of the wireless power transmission system; may communicate through said network to any other system computer; and may be a wireless power transmitter, a wireless power receiver, a client device, a management service server, or any other.

“Transmitter” refers to a device, including a chip which may generate two or more RF signals, at least one RF signal being phase shifted and gain adjusted with respect to other RF signals, substantially all of which pass through one or more RF antenna such that focused RF signals are directed to a target.

“User” refers to a person using the system to provide wireless power transmission to a client device. User may be an operator.

“WIFI” refers to wireless network.

“Wireless power transmission” refers to transmitting energy wirelessly.

DESCRIPTION OF THE DRAWINGS

The present disclosure describes methods for automatically testing the communication between wireless power transmitter and wireless power receiver, i.e. a transmitter to receiver auto test.

Methods disclosed here may be part of a wireless power transmission system including one or more wireless power transmitters, one or more wireless power receivers, and including one or more optional system management server or one or more optional mobile or hand-held computers, smart phones, or the like, that run the system management GUI app. This app may be made available at, downloaded, and installed from a public software app store or digital application distribution platform, such as Apple's iTunes, Google's Play Store, Amazon's Appstore, and the like.

The power transmitters and management servers may all communicate with each other through a distributed system database, and may also communicate present status and any status change to a remote information service that may be located in the Internet cloud.

One or more wireless power transmitters may automatically transmit power to any single wireless power receiver that is close enough for it to establish a communication connection with, using a suitable communication technology, including Bluetooth Low Energy or the like. Said receiver may then power or charge an electrically connected client device, such as mobile device, toy, remote control, lighting device, and the like. A single wireless power transmitter may also power multiple wireless power receivers simultaneously.

Alternately, the system can be configured by the system management GUI to automatically only transmit power to specific wireless power receivers depending on specific system criteria or conditions, such as the time or hour of the day for automatic time-based scheduled power transmission, power receiver physical location, owner of client device, or other any other suitable conditions and/or criteria.

The wireless power receiver is connected electrically to a client device, such a mobile phone, portable light, TV remote control, or any device that would otherwise require a battery or connection to wall power. In one or more embodiments, devices requiring batteries can have traditional batteries replaced by wireless power receiver batteries. The wireless power receiver then receives energy transmitted from the power transmitter, into receiver's antenna, rectifies, conditions, and sends the resulting electrical energy, through an electrical relay switch, to the electrically connected client device to power it or charge it.

A wireless power transmitter can transmit power to a wireless power receiver, which, in response, can power or charge its associated client device while device is in use or in motion anywhere within the power transmission range of the wireless power transmitter. The wireless power transmitter can power multiple devices at the same time.

The wireless power transmitter establishes a real-time communication connection with each receiver for the purpose of receiving feedback in real-time (such as 100 samples per second). This feedback from each receiver includes the measurement of energy presently being received, which is used by the transmitter to control the direction of the transmitter's antenna array so that it stays aimed at the receiver, even if the receiver moves to a different physical 3-D location or is in 3-D motion that changes its physical 3-D location.

Multiple wireless power transmitters can power a given, single receiver, in order to substantially increase power to it.

When a transmitter is done transmitting power to a receiver, it may communicate to the receiver that power transmission has ended, and disconnect communication. The wireless power transmitter may then examine its copy of the distributed system database to determine which, if any, receivers in power range it should next transmit power to.

FIG. 1 illustrates wireless power transmission 100 using pocket-forming. A transmitter 102 may transmit controlled Radio Frequency (RF) waves 104 which may converge in 3-D space. RF waves 104 may be controlled through phase and/or relative amplitude adjustments to form constructive and destructive interference patterns (pocket-forming). Pockets of Energy 106 may form at constructive interference patterns and may be 3-Dimensional in shape, whereas null-spaces may be generated at destructive interference patterns. A Receiver 108 may then utilize Pockets of Energy 106 produced by pocket-forming for charging or powering an electronic device, for example a laptop computer 110, and thus providing wireless power transmission 100. In embodiments disclosed here, there may be two or more transmitters 102 and one or more receivers 108 for powering various electronic devices. Examples of suitable electronic devices may include smartphones, tablets, music players, and toys, amongst others. In other embodiments, adaptive pocket-forming may be used to regulate power on suitable electronic devices.

FIG. 2 illustrates a component level embodiment for a transmitter 202 which may be utilized to provide wireless power transmission 100 as described in FIG. 1. Transmitter 202 may include a housing 204 where at least two or more antenna elements 206, at least one RF integrated circuit (RFIC 208), at least one digital signal processor (DSP) or micro-controller 210, and one optional communications component 212 may be included. Housing 204 can be made of any suitable material which may allow for signal or wave transmission and/or reception, for example plastic or hard rubber. Antenna elements 206 may include suitable antenna types for operating in suitable frequency bands, such as 900 MHz, 2.5 GHz, or 5.8 GHz, and any other frequency bands that may conform to Federal Communications Commission (FCC) regulations part 18 (Industrial, Scientific and Medical equipment) or any other suitable regulations. Antenna elements 206 may include vertical or horizontal polarization, right hand or left hand polarization, elliptical polarization, or other suitable polarizations as well as suitable polarization combinations. Suitable antenna types may include, for example, patch antennas with heights from about ⅛ inches to about 6 inch and widths from about ⅛ inches to about 6 inch. Other antenna elements 206 types may be used, including meta-materials, dipole antennas, and others. RFIC 208 may include a chip for adjusting phases and/or relative magnitudes of RF signals, which may serve as inputs for antenna elements 206 for controlling pocket-forming. These RF signals may be produced using an external power supply 214 and a local oscillator chip (not shown) using a suitable piezoelectric materials. Micro-controller 210 may then process information sent by a receiver through its own antenna elements for determining optimum times and locations for pocket-forming. In some embodiments, the foregoing may be achieved through communications component 212. Communications component 212 may be based on standard wireless communication protocols which may include Bluetooth, Bluetooth Low Energy, Wi-Fi, and/or ZigBee, amongst others. In addition, communications component 212 may be used to transfer other information, including identifiers for the device or user, battery level, location or other such information. The micro-controller may determine the position of a device using any suitable technology capable of triangulation in communications component 212, including radar, infrared cameras, and sound devices, amongst others.

Multiple transmitter 202 units may be placed together in the same area to deliver more power to individual power receivers or to power more receivers at the same time, said power receivers being within power reception range of two or more of multiple power transmitters 202.

FIG. 3 illustrates a component level embodiment for a receiver 300 which may be used for powering or charging an electronic device as exemplified in wireless power transmission 100. Receiver 300 may include a housing 302 where at least one antenna element 304, one rectifier 306, one power converter 308 and an optional communications component 310 may be included. Housing 302 can be made of any suitable material which may allow for signal or wave transmission and/or reception, for example plastic or hard rubber. Housing 302 may be an external hardware that may be added to different electronic equipment, for example in the form of cases, or may be embedded within electronic equipment as well. Antenna element 304 may include suitable antenna types for operating in frequency bands similar to the bands described for transmitter 202 from FIG. 2. Antenna element 304 may include vertical or horizontal polarization, right hand or left hand polarization, elliptical polarization, or other suitable polarizations as well as suitable polarization combinations. Using multiple polarizations can be beneficial in devices where there may not be a preferred orientation during usage or whose orientation may vary continuously through time, for example a smartphone or portable gaming system. On the contrary, for devices with well-defined orientations, for example a two-handed video game controller, there might be a preferred polarization for antennas which may dictate a ratio for the number of antennas of a given polarization. Suitable antenna types may include patch antennas with heights from about ⅛ inches to about 6 inch and widths from about ⅛ inches to about 6 inch. Patch antennas may have the advantage that polarization may depend on connectivity, i.e. depending on which side the patch is fed, the polarization may change. This may further prove advantageous as a receiver, such as receiver 300, may dynamically modify its antenna polarization to optimize wireless power transmission. Rectifier 306 may include diodes or resistors, inductors or capacitors to rectify the alternating current (AC) voltage generated by antenna element 304 to direct current (DC) voltage. Rectifier 306 may be placed as close as is technically possible to antenna element 304 to minimize losses. After rectifying AC voltage, DC voltage may be regulated using power converter 308. Power converter 308 can be a DC-DC converter which may help provide a constant voltage output, regardless of input, to an electronic device, or as in this embodiment to a battery 312. Typical voltage outputs can be from about 5 volts to about 10 volts. Lastly, communications component 310, similar to that of transmitter 202 from FIG. 2, may be included in receiver 300 to communicate with a transmitter 202 or to other electronic equipment.

FIG. 4 shows an exemplary embodiment of a wireless power transmission system 400 (WPTS) in which one or more embodiments of the present disclosure may operate. Wireless power transmission system 400 may include communication between one or more wireless power transmitters 402 and one or more wireless powered receivers 406 and within client device 438. Client device 404 may be paired with an adaptable paired receiver 406 that may enable wireless power transmission to the client device 404. In another embodiment, a client device 438 may include a wireless power receiver built in as part of the hardware of the device. Client device 404 or 438 may be any device which uses an energy power source, such as, laptop computers, stationary computers, mobile phones, tablets, mobile gaming devices, televisions, radios and/or any set of appliances that may require or benefit from an electrical power source.

In one embodiment, one or more wireless power transmitters 402 may include a microprocessor that integrates a power transmitter manager app 408 (PWR TX MGR APP) as embedded software, and a third party application programming interface 410 (Third Party API) for a Bluetooth Low Energy chip 412 (BTLE CHIP HW). Bluetooth Low Energy chip 412 may enable communication between wireless power transmitter 402 and other devices, including power receiver 406, client device 404 and 438, and others. Wireless power transmitter 402 may also include an antenna manager software 414 (Antenna MGR Software) to control an RF antenna array 416 that may be used to form controlled RF waves which may converge in 3-D space and create pockets of energy on wireless powered receivers. In some embodiments, one or more Bluetooth Low Energy chips 412 may utilize other wireless communication protocols, including WiFi, Bluetooth, LTE direct, or the like.

Power transmitter manager app 408 may call third party application programming interface 410 for running a plurality of functions, including the establishing of a connection, ending a connection, and sending data, among others. Third party application programming interface 410 may issue commands to Bluetooth Low Energy chip 412 according to the functions called by power transmitter manager app 408.

Power transmitter manager app 408 may also include a distributed system database 418, which may store relevant information associated with client device 404 or 438, such as their identifiers for a client device 404 or 438, voltage ranges for power receiver 406, location of a client device 404 or 438, signal strength and/or any other relevant information associated with a client device 404 or 438. Database 418 may also store information relevant to the wireless power network, including receiver ID's, transmitter ID's, end-user handheld devices, system management servers, charging schedules, charging priorities and/or any other data relevant to a wireless power network.

Third party application programming interface 410 at the same time may call power transmitter manager app 408 through a callback function which may be registered in the power transmitter manager app 408 at boot time. Third party application programming interface 410 may have a timer callback that may go for ten times a second, and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or a message is received.

Client device 438 may include a power receiver app 420 (PWR RX APP), a third party application programming interface 422 (Third party API) for a Bluetooth Low Energy chip 424 (BTLE CHIP HW), and an RF antenna array 426 which may be used to receive and utilize the pockets of energy sent from wireless power transmitter 402.

Power receiver app 420 may call third party application programming interface 422 for running a plurality of functions, including establishing a connection, ending a connection, and sending data, among others. Third party application programming interface 422 may have a timer callback that may go for ten times a second, and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or message is received.

Client device 404 may be paired to an adaptable power receiver 406 via a BTLE connection 428. A graphical user interface (GUI 430) may be used to manage the wireless power network from a client device 404. GUI 430 may be a software module that may be downloaded from any suitable application store and may run on any suitable operating system, including iOS and Android, amongst others. Client device 404 may also communicate with wireless power transmitter 402 via a BTLE connection 428 to send important data, such as an identifier for the device, battery level information, geographic location data, or any other information that may be of use for wireless power transmitter 402.

A wireless power manager 432 software may be used in order to manage wireless power transmission system 400. Wireless power manager 432 may be a software module hosted in memory and executed by a processor inside a computing device 434. The wireless power manager 432 may include a local application GUI, or host a web page GUI, from where a user 436 may see options and statuses, as well as execute commands to manage the wireless power transmission system 400. The computing device 434, which may be cloud-based, may be connected to the wireless power transmitter 402 through standard communication protocols, including Bluetooth, Bluetooth Low Energy, Wi-Fi, or ZigBee, amongst others. Power transmitter manager app 408 may exchange information with wireless power manager 432 in order to control access by and power transmission to client devices 404. Functions controlled by wireless power manager 432 may include scheduling power transmission for individual devices, prioritizing between different client devices, accessing credentials for each client, tracking physical locations of power receivers relative to power transmitter areas, broadcasting messages, and/or any functions required to manage the wireless power transmission system 400.

FIG. 5 illustrates a wireless power transmission system network 500, according to an exemplary embodiment.

According to some embodiments, wireless power transmission system network 500 may include multiple wireless power transmission systems 502 capable of communicating with a remote information service 504 through internet cloud 506.

In some embodiments, wireless power transmission system 502 may include one or more wireless power transmitters 508, one or more power receivers 510, one or more optional back-up servers 512 and a local network 514.

According to some embodiments, each power transmitter 508 may include wireless power transmitter manager 516 software and a distributed wireless power transmission system database 518. Each power transmitter 508 may be capable of managing and transmitting power to one or more power receivers 510, where each power receiver 510 may be capable of charging or providing power to one or more electronic devices 520.

Power transmitter managers 516 may control the behavior of power transmitters 508, monitor the state of charge of electronic devices 520, and control power receivers 510, keep track of the location of power receivers 510, execute power schedules, run system check-ups, and keep track of the energy provided to each of the different electronic devices 520, amongst others.

According to some embodiments, database 518 may store relevant information from electronic devices 520 such as, identifiers for electronic devices 520, voltage ranges for measurements from power receivers 510, location, signal strength and/or any relevant information from electronic devices 520. Database 518 may also store information relevant to the wireless power transmission system 502 such as, receiver ID's, transmitter ID's, end-user handheld device names or ID's, system management server ID's, charging schedules, charging priorities and/or any data relevant to a power transmission system network 500.

Additionally, in some embodiments, database 518 may store data of past and present system status.

The past system status data may include details such as the amount of power delivered to an electronic device 520, the amount of energy that was transferred to a group of electronic devices 520 associated with a user, the amount of time an electronic device 520 has been associated to a wireless power transmitter 508, pairing records, activities within the system, any action or event of any wireless power device in the system, errors, faults, and configuration problems, among others. Past system status data may also include power schedules, names, customer sign-in names, authorization and authentication credentials, encrypted information, physical areas of system operation, details for running the system, and any other suitable system or user-related information.

Present system status data stored in database 518 may include the locations and/or movements in the system, configuration, pairing, errors, faults, alarms, problems, messages sent between the wireless power devices, and tracking information, among others.

According to some exemplary embodiments, databases 518 within power transmitters 508 may further store future system status information, where the future status of the system may be forecasted or evaluated according to historical data from past system status data and present system status data.

In some embodiments, records from all device databases 518 in a wireless power transmission system 502 may also be stored and periodically updated in server 512. In some embodiments, wireless power transmission system network 500 may include two or more servers 512. In other embodiments, wireless power transmission system network 500 may not include any servers 512.

In another exemplary embodiment, wireless power transmitters 508 may further be capable of detecting failures in the wireless power transmission system 502. Examples of failures in power transmission system 502 may include overheating of any component, malfunction, and overload, among others. If a failure is detected by any of wireless power transmitters 508 within the system, then the failure may be analyzed by any wireless power transmitter manager 516 in the system. After the analysis is completed, a recommendation or an alert may be generated and reported to owner of the power transmission system or to a remote cloud-based information service, for distribution to system owner or manufacturer or supplier.

In some embodiments, power transmitters 508 may use network 514 to send and receive information. Network 514 may be a local area network, or any suitable communication system between the components of the wireless power transmission system 502. Network 514 may enable communication between power transmitters, system management servers 512 (if any), and other power transmission systems 502 (if any), amongst others.

According to some embodiments, network 514 may facilitate data communication between power transmission system 502 and remote information service 504 through internet cloud 506.

Remote information service 504 may be operated by the owner of the system, the manufacturer or supplier of the system, or a service provider. Remote management system may include business cloud 522, remote manager software 524, and one or more backend servers 526, where the remote manager software 524 may further include a general database 528. Remote manager software 524 may run on a backend server 526, which may be a one or more physical or virtual servers.

General database 528 may store additional backups of the information stored in the device databases 518. Additionally, general database 528 may store marketing information, customer billing, customer configuration, customer authentication, and customer support information, among others. In some embodiments, general database 528 may also store information, such as less popular features, errors in the system, problems report, statistics, and quality control, among others.

Each wireless power transmitter 508 may periodically establish a TCP communication connection with remote manager software 524 for authentication, problem report purposes or reporting of status or usage details, among others.

FIG. 6 is a flowchart showing a method for automatic initiation at boot 600 of a power transmitter self-test, according to an exemplary embodiment.

The method for automatic initiation at boot 600 of a power transmitter (PT) self-test may start when a PT manager boots-up 602 a PT. Subsequently, PT may scan 604 for all power receivers (PR) within communications range. For each PR found, wireless power transmission system may command PT to perform 606 a communication self-test for a finite period of time, and then PT stops 608 the communication self-test. If the PT finds a problem 610 during the self-test, PT manager may generate 612 a report to inform a user, at a computing device, of the problem. Afterwards, PT may start its normal operation 614.

FIG. 7 is a flowchart showing a method for automatic initiation during normal operation 700 of a PT self-test, according to an exemplary embodiment.

Periodically, a wireless power transmission system may automatically initiate an automatic self-test and report outcome to system user. The wireless power transmission system may automatically initiate test of an individual system unit or end-to-end test of complete system. Control of automatic initiation of test for one or more PTs by system may be configured by user. Control of automatic initiation may include when to start automatically initiated test, what to test, and how long to run the automatic test, among other parameters.

The method for automatic initiation during normal operation 700 of a PT self-test may start when a wireless power transmission system receives a user configuration 702 from a user computing device. User configuration 702 may be through a system management GUI web site hosted by the system management service that is cloud based or on a local server, or through a system management GUI app running on the user's mobile computing device.

Following user configuration 702, PT may start its normal operation 704, during which PT manager may employ the user configuration 702 to check 706 if it's time to perform the self-test. If current time does not correspond with the user configuration 702, PT may continue with its normal operation 704. If current time does correspond with the user configuration 702, wireless power transmission system may command each configured PT to perform 708 a communication self-test. Subsequently, after the period of time has been completed, according to user configuration 702, wireless power transmission system may command the PTs whose period has been completed to stop 710 self-test. Wireless power transmission system may then check 712 if testing has been performed long enough. If self-test has not been performed long enough, wireless power transmission system may command each configured PT to again perform 708 communication self-test. If self-test has been performed long enough PT manager application may send a report 714 of the outcome to the user computing device and inform the user that the automatic self-test has been performed.

FIG. 8 is a flowchart showing a method for manual initiation 800 of a PT self-test, according to an exemplary embodiment.

A user may employ a computing device and manually start a self-test of a single PT, specific set of PTs, or all system PTs. Manual initiation 800 of self-test may be commanded by a user computer device operating the system management GUI, either an app running on a user computing device, or a web site hosted by a system management server.

The method for manual initiation 800 of a PT self-test may start during PT normal operation 802. A user employs a computing device to configure 804 the test and subsequently command 806 a wireless power transmission system to start the test. The wireless power transmission system may then start 808 the test commanding 810 each configured PT to perform 812 the self-test. The algorithm employed by the wireless power transmission system to command the start of the test may be performed by a PT manager application in a wireless power transmission system cloud or a PT application running on the user computing device. The user, by means of a computing device, may specify the duration of test at start.

Wireless power transmission system may then check 814 if testing has been performed long enough. If self-test has not been performed long enough, wireless power transmission system may command the next configured PT to perform 812 a communication self-test. PT self-test may run indefinitely until self-test has been performed long enough or test is ended by a user by means of a computing device.

If self-test has been performed long enough or test is ended by a user computing device, then PT manager application may send a report 816 of the outcome to the user at the system management GUI and inform the user that the automatic self-test has been performed.

FIG. 9 is a flowchart showing a method for performing a PT communication self-test 900, according to an exemplary embodiment.

In one embodiment, when a PT boots-up, PT may scan for all PRs within the communication range. For each PR found, PT may perform an automatic communication self-test for a finite period of time, and then PT may stop self-test and may start normal operation. Once boot-time communication self-test has passed, PT may periodically check if a command to run self-test has been communicated to it from system management software that is external to the PT.

In other embodiments, wireless power transmission system may periodically automatically initiate the automatic communication self-test and report outcome to system user. The system may automatically initiate the communication self-test of an individual system unit or an end-to-end test of the complete system. Control of automatic initiation of test by system may be configured by a user.

In another embodiment, a user may manually start self-test of a single transmitter, specific set of transmitters, or all system transmitters. Communication self-test may run indefinitely until stopped by user, or user may specify duration of test at start.

In some embodiments, a wireless power transmission system management software may communicate the self-test command to a PT in response to a user command entered at a client device that is running a system mobile management app, or at the system web page that is hosted by the system management server.

In some embodiments, a wireless power transmission system management software may communicate the self-test command to a PT automatically in response to some trigger event, such as the passage of a finite amount of time, or other. The command may indicate that the PT should run the test until commanded to stop, or run the test for a specific duration.

Method for performing a PT communication self-test 900 may start when a wireless power transmission system's management application software, running on a system management server, selects 902 a PT to test. Subsequently, the selected PT may scan for all PRs within communication range. For each PR found, the PT may connect 904 and then initiate communication interchange 906 with PR. Communication interchange 906 may be in real-time. Once communication is established, the PT may perform any suitable type of system message exchange, employing any suitable type of system message between the PT and the PR. Then, PT may periodically disconnect and re-connect 908 from PR, in order to test re-connection. PT may update metrics counters with software actions and operations.

Afterwards, wireless power transmission manager app may check 910 if there is a problem of communication between PT and PR. If a problem is found, PT manager application may generate 912 a report to send to the wireless power transmission manager app on the system management server any unexpected patterns of metrics counters or, unexpected operation, or any test failure. If a problem is not found, PT may report that self-test passed to the wireless power transmission manager application.

The wireless power transmission manager app may then check 914 if testing has been performed long enough. If self-test has not been performed long enough, PT may connect 904 to the next PR, and then initiate communication interchange 906 with PR. If self-test has been performed long enough PT manager application may signal 916 the PR that the self-test has ended, and then end communication with PR.

PT may check 918 if there are other PRs to be tested and subsequently connect 904 with a PR to test and begin the process of method for performing a PT communication self-test 900. If there are no other PRs to be tested, the process may end and tested PT may begin normal operation.

If transmitter started the test at boot, then test may end after a finite duration that may be set or hard-coded in the system software.

If test was started by external management software to run for a finite duration, then test may end when transmitter determines that duration has elapsed.

If test was started by external management software to run indefinitely, then test may only end when external management software communicates a command to transmitter to end the test.

After the communication self-test ends, each PT performing the self-test may end communication connection with latest PR being tested. PRs may begin normal operation.

The counts of all actions and operations, performed by the wireless power transmission system while testing connections and communication may be stored in metrics counters within a database. When the PT communication self-test 900 is complete, said metrics counters may be compared with expected values. If said metrics counters match the expected values, then test passed, otherwise test failed. The wireless power transmission system may report to the user computing device the outcome of the test.

Examples

Example #1 is an embodiment of the application of method for performing a PT communication self-test 900, where a wireless power transmission system is being used in an office environment. The office environment includes a first and second wireless power transmitter, the two of which are in communication with a wireless power management service running on a server in the IT department. In example #1, the wireless power transmission system receives a command from a user computing device stating that the computing device is to be charged, and the wireless power transmission manager proceeds to command the PT within the communication range of the user computing device to perform PT communication self-test 900 as described in FIG. 9. The PT looks up in its copy of the system database the PR that powers said computing device. When checking the communication between the PT and the PR, unexpected patterns of metrics counters are identified and the self-test fails. The power transmitter manager software within the tested PT then generates a report including the information of the outcome of the self-test and communicates the generated report to the computing device, which is running the system management GUI, which notifies user computing device of test result.

The foregoing method descriptions and the process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by one of skill in the art the steps in the foregoing embodiments may be performed in any order. Words such as “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Although process flow diagrams may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

Embodiments implemented in computer software may be implemented in software, firmware, middleware, microcode, hardware description languages, or any combination thereof. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the invention. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code being understood that software and control hardware can be designed to implement the systems and methods based on the description herein.

When implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module which may reside on a computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable media includes both computer storage media and tangible storage media that facilitate transfer of a computer program from one place to another. A non-transitory processor-readable storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such non-transitory processor-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible storage medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer or processor. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.

The preceding description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein. 

What is claimed is:
 1. A power system, comprising: a plurality of antenna elements; a radio-frequency (RF) circuit, operatively coupled to the plurality of antenna elements; a processing apparatus, operatively coupled to the RF circuit, wherein the processing apparatus is configured to cause the RF circuit and plurality of antenna elements to generate pocket-forming energy in three dimensional space; and communications for communicating with a receiver, configured to receive the pocket-forming energy in three dimensional space, wherein the processing apparatus is configured to perform a self-test of the power system upon the occurrence of a predetermined event.
 2. The power system of claim 1, wherein the predetermined event comprises one of a boot-up, passage of a predetermined period of time, a self-test command received in the communications from the receiver, and a self-test command received in the communications from a server.
 3. The power system of claim 1, wherein the processing apparatus is configured to transmit a result of the self-test via the communications.
 4. The power system of claim 3, wherein the result of the self-test comprises a comparison of the power systems functions to at least one metrics counter.
 5. The power system of claim 4, wherein the comparison comprises determining if patterns of metrics counters are present.
 6. The power system of claim 1, wherein the processing apparatus comprises at least one of a digital signal processor and a microcontroller.
 7. The power system of claim 1, wherein the communications comprise one of WiFi, Bluetooth and LTE.
 8. A method of operating a power system, comprising: configuring a processing apparatus to activate a RF circuit operatively coupled to a plurality of antenna elements to generate pocket-forming energy in three dimensional space; and configuring communications to communicate with a receiver configured to receive the pocket-forming energy in three dimensional space, performing, via the processing apparatus a self-test of the power system upon the occurrence of a predetermined event.
 9. The method of claim 8, wherein the predetermined event comprises one of a boot-up, passage of a predetermined period of time, a self-test command received in the communications from the receiver, and a self-test command received in the communications from a server.
 10. The method of claim 8, further comprising the step of transmitting a result of the self-test via the communications.
 11. The method of claim 10, wherein the result of the self-test comprises a comparison of the power system functions to at least one metrics counter.
 12. The method of claim 11, wherein the comparison comprises determining if patterns of metrics counters are present.
 13. The method of claim 8, wherein the processing apparatus comprises at least one of a digital signal processor and a microcontroller.
 14. The method of claim 8, wherein the communications comprise one of WiFi, Bluetooth and LTE.
 15. A power system, comprising: a plurality of antenna elements; a radio-frequency (RF) circuit, operatively coupled to the plurality of antenna elements the RF circuit being configured to adjust at least one of phase and magnitude of RF signals provided to the plurality of antenna elements; a processing apparatus comprising at least one of a microcontroller and a digital signal processor (DSP), operatively coupled to the RF circuit, wherein the processing apparatus is configured to cause the RF circuit and plurality of antenna elements to generate pocket-forming energy in three dimensional space; and communications for communicating with a receiver, configured to receive the pocket-forming energy in three dimensional space, wherein the processing apparatus is configured to perform a self-test of the power system upon the occurrence of a predetermined event.
 16. The power system of claim 15, wherein the predetermined event comprises one of a boot-up, passage of a predetermined period of time, a self-test command received in the communications from the receiver, and a self-test command received in the communications from a server.
 17. The power system of claim 15, wherein the processing apparatus is configured to transmit a result of the self-test via the communications.
 18. The power system of claim 17, wherein the result of the self-test comprises a comparison of the power systems functions to at least one metrics counter.
 19. The power system of claim 18, wherein the comparison comprises determining if unexpected patterns of metrics counters are present.
 20. The power system of claim 15, wherein the communications comprise one of WiFi, Bluetooth and LTE. 